-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New & old remembered sets #418
New & old remembered sets #418
Conversation
Failing tests are from JIT, they are already broken on |
(self isPermanent: objOop) ifTrue: [ | ||
(self isOld: valuePointer) ifTrue: [ | ||
self possiblePermStoreInto: objOop ] ]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(self isRemembered: destObj) ifFalse: | ||
[scavenger remember: destObj] | ||
((self isRemembered: destObj) and: [ | ||
newSpaceRememberedSet isInRememberedSet: destObj ]) ifFalse: [ | ||
newSpaceRememberedSet remember: destObj ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isRemembered
boolean is not enough because you don't know in which remembered set is. And is possible for an object to be in both.
We should measure if this affect performance and maybe improve the strategy.
Now we have 2 remembered sets:
And:
fullGC
.